5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

VERIFY


The VERIFY statement causes various functions from the File Management's Verify File Menus to be executed from within a process.

  ?????   VERIFY   ??? ?????????????????????? ??? TYPE ?????????????? FAIL ?
  (1)              (2) (3)                    (4)      (5)                (6)

(1) T/F execution conditions
(2) Application ID
(3)File name or field name
(4) Occurrence (constant/index)
(5) Verify type (FIELD, RECORD)
(6) Fail action (0=nothing, 1=warning, 2=error, 3=cancel)

Sets True/False Status Indicator

The next level of the internal true/false status indicator is set to T if the VERIFY operation is successful; otherwise, the indicator is set to F. If the VERIFY fails, the FAIL parameter determines what additional action to take.

Using the Statement

A file can be verified to insure that it is structurally sound and that each field (or a specific field) contains data that corresponds to the field type (number, date, etc.).

The TYPE parameter indicates what component of the file to verify. The only valid choices, among those presented in a drop-down list, are:

FIELD to verify the contents of a particular field within every record of the file (field name required).

RECORD to verify the contents of all fields within the current record (file name required).

The application ID and file name for the file (or field) to verify are specified in the statement. Additional information that can affect the location of the file may be contained in the predefined field DATABASE.

The file name references a file that is defined in the data dictionary for the selected application ID. You can set the NEXT DATABASE predefined field to the database ID of the database containing the file that you want verified if it is different than the current database.

Execution Errors

Serious problems encountered while trying to verify a file or its contents, such as a file structure/data dictionary mismatch, cause a non-recoverable runtime error to occur, regardless of the FAIL parameter.

Related PDFs

DATABASE, NEXT DATABASE

Related Statements

OPEN, CLOSE

Example

The following example verifies the contents of the CUSTOMER BALANCE field and returns an error if an inconsistency is found between the Data Dictionary field type and the actual contents of the field in all CUSTOMER file records. 

          VERIFY   TAR CUSTOMER BALANCE                   TYPE FIELD  FAIL 0
  F       CANCEL   Verification of TAR CUSTOMER BALANCE Field Failed!

Application Design Manual                                         "Powered by Appx Software"

711

©2006 By APPX Software, Inc. All Rights Reserved